Introduces a new standalone :testharness Android application module for
end-to-end validation of Bitwarden's Credential Manager provider and
Autofill framework implementations.

Purpose:
The test harness acts as a credential consumer client, allowing developers
to trigger and verify all credential operations that Bitwarden supports as
a provider without relying on external websites or applications.

Supported Test Flows:
- Password Creation: CreatePasswordRequest via Credential Manager
- Password Retrieval: GetPasswordOption via Credential Manager
- Passkey Creation: CreatePublicKeyCredentialRequest (FIDO2)
- Passkey Authentication: GetPublicKeyCredentialOption (FIDO2)
- Hybrid Operations: Combined password/passkey retrieval flows
- Origin Parameter Testing: Privileged app simulation with custom origins
- Autofill Framework: Placeholder for future autofill service testing

Architecture:
- MVVM + UDF: BaseViewModel with State/Action/Event patterns
- Hilt DI: Full dependency injection throughout all layers
- Jetpack Compose: Material 3 UI with BitwardenTheme integration
- Navigation: Multi-screen architecture matching :app and :authenticator
- Error Handling: Sealed Result classes, no exception-based handling

Module Structure:
- Activity layer: MainActivity with theme management
- Navigation: RootNavScreen orchestrating all test flows
- Data layer: CredentialTestManager wrapping AndroidX Credentials APIs
- UI layer: Feature screens for each credential operation type
- Test coverage: Comprehensive unit tests for all ViewModels and Screens

Build Configuration:
- Added :testharness to settings.gradle.kts
- Integrated with detekt static analysis
- Integrated with kover code coverage reporting
- API 28+ requirement (AndroidX Credentials with Play Services)

Requirements:
- Android API 28+
- Bitwarden app installed as credential provider
- Google Play Services (for API 28-33 compatibility)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

This commit addresses UI layout issues on testharness screens, particularly on devices with smaller displays where content could be pushed off-screen or overflow when the software keyboard is visible.

The primary change is removing fixed heights and weights from the result `OutlinedTextField` components across multiple screens. These modifiers were making the text fields inflexible, preventing the layout from shrinking to accommodate the keyboard. By removing them, the text fields now dynamically resize based on their content, allowing the entire screen to scroll when necessary.

Specific changes:
- Removed fixed height and weight modifiers from result text fields in `CreatePasswordScreen`, `GetPasskeyScreen`, `GetPasswordScreen`, `CreatePasskeyScreen`, and `GetPasswordOrPasskeyScreen` to allow them to resize with their content.
- Added vertical scrolling to `GetPasswordOrPasskeyScreen` to ensure all fields remain accessible when the keyboard is open.
- Added bottom navigation bar padding to the `LandingScreen` to prevent the last button from being obscured by system navigation gestures.

Adds navigationBarsPadding Spacer at the bottom of:
- CreatePasswordScreen
- GetPasswordScreen

This ensures proper edge-to-edge display support and prevents
content from being obscured by system navigation bars,
maintaining consistency with other screens in the testharness.

Addresses PR #6159 review feedback

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Inject a fixed `Clock` into the Credential-related view models (`CreatePasskeyViewModel`, `GetPasskeyViewModel`, `CreatePasswordViewModel`, `GetPasswordViewModel`, and `GetPasswordOrPasskeyViewModel`).

This ensures that any time-dependent logic within these view models becomes deterministic, preventing potential flakiness in the corresponding tests. Previously, the view models relied on the system clock, which could lead to unpredictable behavior during test execution. This change makes the tests more reliable and repeatable.

Refactor the Credential Manager list navigation to use root push transitions and improve the screen's layout handling of system insets.

- Switch `CredentialManagerListRoute` to use `composableWithRootPushTransitions` instead of the standard `composable` builder to ensure consistent transition animations.
- Extract the screen instantiation into a private `credentialManagerListDestination` composable helper.
- Add `navigationBarsPadding` and vertical spacing to the bottom of `CredentialManagerListScreen` to prevent content from being obscured by the system navigation bar.
- Apply minor formatting improvements to the event handling logic in `CredentialManagerListScreen`.

Refactor navigation logic in the `testharness` module to use consistent transition patterns and improve UI scrolling behavior. Additionally, replace hardcoded strings with localized resources for accessibility content descriptions.

- Refactor `AutofillPlaceholderNavigation` and `CredentialManagerListNavigation` to encapsulate screen definitions within `NavGraphBuilder` extension functions. These functions now directly utilize `composableWithRootPushTransitions`, ensuring consistent transition animations and cleaner graph definitions.
- Update `CredentialManagerListScreen` to attach the `nestedScrollConnection` from the `scrollBehavior` to the `BitwardenScaffold`. This enables proper nested scrolling interactions with the pinned top app bar.
- Replace the hardcoded "Back" content description with `stringResource(BitwardenString.back)` across all feature screens (`CreatePasswordScreen`, `CreatePasskeyScreen`, `GetPasswordScreen`, `GetPasskeyScreen`, `GetPasswordOrPasskeyScreen`, and `CredentialManagerListScreen`) to ensure consistency and proper localization support.
- Delete the unused helper script `.claude/skills/reviewing-changes/scripts/detect-threads.sh`.